Comments
-
Same. Issues seems to be resolved. If you device is unresponsive manually power cycle it and it should come back online and be stable.
-
Yea I had some that weren't rebooting by themselves and some that were. Looks like issue is mostly fixed but the one's that are unresponsive need to be manually power cycled. After that I have not had any issues with those devices so for (+15).
-
Sonicwall pushed a KB about it: Dear SonicWall Partners, If you’re customers are experiencing issues with their Gen 7 Firewalls starting last night, please refer to the workaround fix below. Formal communication should come out but use this in the meantime to get ahead of this issue.
-
If the issue just start last night/today it is related to a bigger issue on the backend that sonicwall is having. Dear SonicWall Partners, If you’re customers are experiencing issues with their Gen 7 Firewalls starting last night, please refer to the workaround fix below. Formal communication should come out but use this…
-
Yes. From what I can tell it is only Gen 7 devices on the latest 2 or 3 versions of the firmware. I have noticed some need to be manually restarted then they will restart themselves and I now have a couple that are stable. Others I cant get to.
-
Same issue
-
@SuroopMC I have tried using 4.6.x and the issue continues. I then tried running the commands previously supplied: - sentinelctl config -p agent.vssConfig.enableResearchDataCollectorVssWriter -v false -k "Agent passphrase" - sentinelctl config -p agent.vssConfig.enableStaticResearchDataCollectorVssWriter -v false -k "Agent…
-
@SuroopMC My issue is actually with Quest Rapid Recovery. That being said the latest available agent is 4.6.14.304 for windows. I've had this case open with you since March
-
Here is my experience so far hope it is helpful for anyone. I am coming from CC 3.1 portal. Any updates I have done so far have not been an issue. Device may need to be rebooted before updating. The licensing and duplicate entries on the 3.6 portal are also not an issue. Now the issues: Looks like all my policies when…
-
You shouldn't have to manually create the rule. Under the advanced tab of the VPN Policy there is a section to allow management through the VPN. Just check the box and it will create the rule automatically.
-
Yes this issue is with S1 4.1.6.118. It is happening on multiple systems in different client environments with the common factor Capture Client 3.1.4 S1 4.1.6.118. Moving to this version of S1 has fixed the issue of the backup failing every time it is trying to run. Now it fails a couple of times a day with the following…
-
Week and half later and still no updates from support.
-
@ThomTurner It hasn't.
-
Yes I can confirm this is working now. Any plans to fix the straight upgrade from 4.1.5.97 to 4.1.6.118 without having to uninstall and reinstall?
-
I can manually install version 4.1.6.118 successfully on test machine Will try on production machine giving me issue tonight You should really pull these knowledgebase articles with steps for install that don't work.